-
Notifications
You must be signed in to change notification settings - Fork 542
CCXDEV-14850: align insights DataGather with config #2248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CCXDEV-14850: align insights DataGather with config #2248
Conversation
@opokornyy: This pull request references CCXDEV-14850 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Hello @opokornyy! Some important instructions when contributing to openshift/api: |
af4174b
to
4bada1b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe most of this API I've seen before and looks good. I've left comments on stuff that seemed new to me
4725f08
to
866a461
Compare
Just leaving a general note that some of the changes I've requested are a deviation from the v1alpha1 API that I think would be inherently breaking (i.e removing fields, etc.). I'm still learning what this means for alpha level APIs that are only in TPNU clusters, but I suspect we would likely want to go back and bring the v1alpha1 APIs into alignment (or drop them?). @JoelSpeed what is the correct approach to follow here? |
Since we aren't going to allow clusters to upgrade between v1alpha1 and v1alpha2, we don't need to make changes in the alpha 1 or care about conversion webhooks, so we can make breaking changes here |
811a9a2
to
d548836
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple more comments plus my still outstanding comment on the TotalRisk
field.
Other than that, I think this looks good.
@JoelSpeed will need to make a pass on it prior to it being able to merge though
d548836
to
0fa9cfb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple more comments. Other than these, I think it looks good.
tagging in @JoelSpeed for a review.
0fa9cfb
to
882784e
Compare
bb217af
to
522fbdc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have any additional comments on this PR. Looks like the only outstanding comment is from @JoelSpeed related to the None
gathering mode.
522fbdc
to
c73b718
Compare
This commit introduces the v1alpha2 version of the DataGather CRD for Insights. Signed-off-by: Ondrej Pokorny <[email protected]>
b32ffb8
to
1806f37
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of small bits to fix around wording, please add those bits about starting and ending to both the godoc and the CEL error message.
And fix the validation on resource from 1123 to 1035 label as there is a subtle difference
const ( | ||
TotalRiskLow TotalRisk = "Low" | ||
TotalRiskModerate TotalRisk = "Moderate" | ||
TotalRiskImportant TotalRisk = "Important" | ||
TotalRiskCritical TotalRisk = "Critical" | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Why Low/Moderate/Important/Critical? I was expecting High to follow Moderate
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a strong opinion, but I'll ask @tremes whether this naming was introduced in IO and if it's okay to change it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reflects the severity levels defined for the Insights recommendation so it's not easy to change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack, that's ok then, just felt like it didn't fit, but if it's already shipped it's already shipped
This commit aligns the configuration options of the DataGather CRD with those of InsightsDataGather, making it easier to use both CRDs. Signed-off-by: Ondrej Pokorny <[email protected]>
1806f37
to
7f939ff
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: everettraven, JoelSpeed, opokornyy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@opokornyy: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
[ART PR BUILD NOTIFIER] Distgit: ose-cluster-config-api |
This PR should align the configuration options in DataGather with the InsightsDataGather